chore: add test fixes and additional debugging - #1270
Conversation
Signed-off-by: Jonathan West <jgwest@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (10)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe E2E tests now protect debug output from typed-nil namespaces, centralize cleanup diagnostics, wait for Route and ArgoCD readiness, retry Redis and Sentinel validation, and use longer health-check timeouts. ChangesE2E reliability
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The PR adjusts end-to-end test timing and failure diagnostics without changing product runtime behavior. No actionable merge-blocking risk remains, so it is merge-ready after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Warning Repository analysis: Couldn't refresh Comment |
|
AWS quota /retest |
|
/lgtm |
What type of PR is this?
/kind failing-test
What does this PR do / why we need it:
Have you updated the necessary documentation?